Methods and apparatus related to management of unit-based virtual resources within a data center environment

ABSTRACT

In one embodiment, a processor-readable medium can be configured to store code representing instructions to be executed by a processor. The code can include code to receive a request to change a value representing a number of data center units included in a set of data center units assigned to a user. Each of the data center units from the set of data center units can be associated with hardware resources managed based on a set of predefined hardware resource limit values. The code can include code to determine, in response to the request, whether hardware resources of a data center unit mutually exclusive from hardware resources of the set of data center units and managed based on the set of predefined resource limit values is available for assignment to the user when the request to change is an increase request.

This application is a Continuation of U.S. application Ser. No. 12/709,962 filed Feb. 22, 2010. The entirety of the above-listed application is incorporated herein by reference.

BACKGROUND

Embodiments described herein relate generally to virtual resources within a data center, and, in particular, to management of unit-based virtual resources within a data center environment.

Because data center environments (e.g., cloud computing data center environments) are defined by a relatively large-scale infrastructure, management of the various components within the infrastructure can be complicated and may not be handled in a desirable fashion using known methods and apparatus. In particular, known methods and apparatus for managing resources of infrastructure to provide a specified level service (e.g., a guaranteed level of service) to users with virtual resources operating within the data center environment may not be adequate for some applications. Many of these known methods and apparatus, for example, may be too specialized for some applications and/or may not integrate the diverse functionality of various systems that control and/or manage components within the data center environment to provide a specified level of service in a desirable fashion.

Thus, a need exists for methods and apparatus for management of unit-based virtual resources within a data center environment.

SUMMARY

In one embodiment, a processor-readable medium can be configured to store code representing instructions to be executed by a processor. The code can include code to receive a request to change a value representing a number of data center units included in a set of data center units assigned to a user. Each of the data center units from the set of data center units can be associated with hardware resources managed based on a set of predefined hardware resource limit values. The code can include code to determine, in response to the request, whether hardware resources of a data center unit mutually exclusive from hardware resources of the set of data center units and managed based on the set of predefined resource limit values is available for assignment to the user when the request to change is an increase request.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a schematic diagram that illustrates a management module, a hardware controller, and a data center, according to an embodiment.

FIG. 2 is a schematic diagram that illustrates a database that can be stored in a memory of a management module, according to an embodiment.

FIG. 3 is a schematic diagram that illustrates a database that includes information about the availability of data center resources, according to an embodiment.

FIG. 4 is a graph that illustrates values of a performance metric, according to an embodiment.

FIG. 5 is a schematic diagram that illustrates resources controller in communication with a data center, according to embodiment.

FIG. 6 is a flowchart that illustrates a method for modifying a set of data center units based on a performance metric, according to an embodiment.

FIG. 7 is a flowchart that illustrates a method for modifying a number of data center units in response to a request, according to an embodiment.

DETAILED DESCRIPTION

FIG. 1 is a schematic diagram that illustrates a management module 130, a resource controller 170, and a data center 100, according to an embodiment. The management module 130 is configured to send one or more instructions to the resource controller 170 (or a portion thereof) to trigger the resource controller 170 to managed one or more hardware resources of the data center units 180 within the data center 100. As shown in FIG. 1, the data center units 180 include data center unit DU1, data center unit DU2, and data center unit DU3. In some embodiments, the data center units 180 can be referred to as a set of data center units. In some embodiments, the hardware resources of a data center unit can also be referred to as processing resources of a data center unit.

As represented by the dashed lines from the data center units 180 to a user 50, the hardware resources of the data center units 180 are managed (e.g., allocated, provisioned, reserved) for use by the user 50 (e.g., for processing associated with the user 50). Said differently, the data center units 180 (or the data center units of the data center units 180) are assigned to the user 50. Because the data center units 180 are assigned to the user 50, the user 50 can use the hardware resources of data center units 180 to, for example, perform one or more functions specified by the user 50. For example, the hardware resources of data center units 180 can be used by the user 50, for example, to operate one or more virtual resources (e.g., virtual machines) (not shown) of the user 50. In some embodiments, the user 50 can be a customer, a client, a company, and/or so forth. In some embodiments, the user 50 can represent a computing element (e.g., a server, a personal computer, a personal digital assistant (PDA)) associated with, for example, a human user.

The data center units 180 can each be managed as a specified portion of resources (e.g., hardware resources, software resources) of the data center 100. In other words, resources of the data center 100 can be divided into (e.g., partitioned into) data center units 180 that can be used, for example, to handle processing associated with one or more virtual resources (for users such as user 50). In some embodiments, the virtual resource(s) can be configured to, for example, emulate the functionality of a physical source device and/or its associated software.

For example, in some embodiments, the hardware resources (and the associated software resources to support the hardware resources) of one or more of the data center units 180 can be managed so that they perform at (or are capable of performing at), for example, predefined hardware resource limit values. Specifically, the hardware resources of one or more of the data center units 180 can managed so that they perform at, for example, a specified level of network bandwidth (e.g., 10 megabits/second (Mb/s) of network bandwidth, a specified level of network bandwidth of more than 1 Mb/s of network bandwidth), a specified level of processing speed (e.g., a processor speed of 300 megahertz (MHz), a processor speed of 600 MHz, a specific processor speed of more than 200 MHz), a specified input/output (I/O) speed of a storage device (e.g., a disk I/O speed of 40 I/O operations per second, a specified disk I/O speed of more than 10 IOPS), and/or a specified storage device bandwidth (e.g., a disk bandwidth of 10 Mb/s, a specified level of disk bandwidth of more than 10 Mb/s). A specified portion of hardware resources can also be reserved as part of one or more of the data center unit(s) 180. For example, the data center unit(s) 180 can also have a specified level of a storage device (e.g., a disk size of 30 gigabytes (GB), a specified disk size of more than 1 GB) and/or a specified memory space (e.g., a memory storage capacity of 768 megabytes (MB), a specified memory storage capacity of more than 64 MB) allocated to the data center unit(s) 180.

In some embodiments, the hardware resources (and accompanying software) of the data center 100 can be partitioned so that the data center units 180 are guaranteed, if necessary, to perform at, or have hardware resources at, the predefined hardware resource limit values. In other words, the hardware resources of the data center units 180 can be managed so that they provide guaranteed levels of service that correspond with each (or every) predefined hardware resource limit value from a set of predefined hardware resource limit values. Said another way, the hardware resources (or portions thereof) of a data center unit from the data center units 180 can be reserved so that they are available for processing associated with the user 50. For example, a first hardware resource (or a portion thereof) (e.g., a memory component) that defines a first portion of data center unit DU3 can provide a guaranteed level of service that corresponds within a first predefined hardware resource limit value from a set of predefined hardware resource limit values, and a second hardware resource (or a portion thereof) (e.g., a network card) that defines a second portion of data center unit DU3 can provide a guaranteed level of service that corresponds within a second predefined hardware resource limit value from the set of predefined hardware resource limit values.

In some embodiments, if one or more of the hardware resources of the data center units 180 are not performing functions for the user 50 (e.g., performing processing of virtual resources associated with the user 50), the hardware resource(s) (or portions thereof) that are associated with the data center units 180 may be idle (or substantially idle). The hardware resource(s) of the data center units 180 will be idle (or substantially idle) so that they are guaranteed to be available for processing for the user 50 when they are needed. In some embodiments, a guaranteed level of service can also be referred to as a guaranteed level of functionality.

In some embodiments, the set of predefined hardware resource limit values (which can be used to define the data center units 180) can be defined based on statistical data based on a predefined set of virtual resources that indicates a particular combination of hardware resources can be used to operate a virtual resource. In some embodiments, for example, a set of predefined hardware resource limit values can be defined based empirical data. Specifically, a hardware resource limit value associated with a particular hardware type (e.g., a disk type) can first be selected. Additional hardware resource limit values associated with other hardware types can be defined based on empirical data related to desirable operation of the additional hardware resources when the particular hardware type is operating at the selected hardware resource limit value. Accordingly, the set of predefined hardware resource limits values can be defined based on the collective performance of the hardware resources using the selected hardware resource limit value as a starting point. In some embodiments, the data center units 180 can be defined by a set of predefined hardware resource limit values so that the data center unit can operate a particular type of virtual resource or set of virtual resources in a desirable fashion (within a particular set of performance specifications).

The hardware resources of the data center units 180 can be managed (e.g., allocated, reserved), at least in part, by the resource controller 170 (or a portion thereof) based on one or more predefined hardware resource limit values. For example, the resource controller 170 can be configured to manage a resource (e.g., a software resource, a hardware resource) of the data center 100, or a portion thereof, to one or more of the data center units 180 based on a predefined hardware resource limit value (e.g., a predefined hardware resource limit value from a set of predefined hardware resource limit values). In other words, the predefined hardware resource limit values can be policed or enforced by the resource controller 170. For example, the resource controller 170 can be configured to manage processing resources of a processor of a host device (not shown) within the data center 100 so that a specified portion of the processing capacity of the processor (which can correspond with a hardware resource limit value) is reserved for the data center unit DU1. The resource controller 170 (or a portion thereof) can be configured to interface with the resources of the data center 100 so that the hardware resources (from the resources of the data center 100) of data center units 180 can provide guaranteed levels of service that correspond with a set of predefined hardware resource limit values. In some embodiments, the resource controller 170 can include one or more specialized resource controllers that are each configured to manage resources associated with a particular type of resource (e.g., a memory type, a central processing unit). More details related to a resource controller and specialized resource controllers are described in connection with FIG. 5.

In some embodiments, the hardware resources of one or more of the data center units 180 can be managed so that only certain predefined hardware resource limit values of the hardware resources of the data center unit(s) 180 are guaranteed. In some embodiments, for example, the hardware resources of data center unit DU1 can be managed by the resource controller 170 (or a portion thereof) so that the hardware resources of data center unit DU1 can provide a guaranteed level of processing speed and have a guaranteed portion of disk space available, but can be managed so that the hardware resources of data center unit DU1 may provide a specified bandwidth speed in only certain situations. Accordingly, the bandwidth speed of the hardware resources of data center unit DU1 is not guaranteed. In such circumstances, the data center unit DU1 can be referred to as a partially guaranteed data center unit.

In some embodiments, the hardware resources of data center units 180 can be managed so that the hardware resources of each of the data center units 180 is managed based on the same set of hardware resource limit values. Accordingly, hardware resources of each data center unit from the data center units 180 may be managed so that they provide the same (or substantially the same) guaranteed level of service.

In some embodiments, the hardware resources of one or more of the data center units 180 can be based on different sets of predefined hardware resource limit values. For example, the hardware resources of data center unit DU1 can be based on a first set of predefined hardware resource limit values and the hardware resources of data center unit DU2 can be based on a second set of predefined hardware resource limit values different than the first set of predefined hardware resource limit values. In such instances, the hardware resources of data center unit DU1 can provide a different guaranteed level of service than the guaranteed level of service provided by hardware resources of data center unit DU2. The resource controller 170 can be configured to managed the hardware resources of these different data center units based on the different sets of predefined hardware resource limit values.

In some embodiments, one or more of the data center units 180 can include software resources. In other words, software resources can be associated with (and can define) at least a portion of the data center unit(s) 180. For example, the hardware resources of data center unit DU1 can have a software resource licensed specifically for operation of and/or operation within the hardware resources of data center unit DU1. In some embodiments, the resource controller 170 (or a portion thereof) can be configured to manage the software resources of the data center 100 so that the software resources are allocated (e.g., assigned), as specified, to the hardware resources of each of the data center units 180.

Resource controllers configured to manage a portion of a data center unit that is hardware-based can be referred to as hardware resource controllers. For example, a data center unit that includes specified allotment of memory can be defined by a hardware controller. Similarly, resource controllers configured to manage a portion of a data center unit that is software-based can be referred to as software resource controllers. Software resources and hardware resources of a data center unit can be collectively referred to as processing resources. Accordingly, the processing resources of a data center unit can be managed by (e.g., collectively managed by) a resource controller.

As shown in FIG. 1, the management module 130 can be in communication with (e.g., can be accessed via) a user interface (UI) 160. The user interface 130 can be configured so that a user (e.g., a data center administrator, a network administrator, a customer, a source owner) can send signals (e.g., control signals, input signals, signals related to instructions) to the management module 130 and/or receive signals (e.g., output signals) from the management module 130. Specifically, the user interface 160 can be configured so that the user can trigger one or more functions to be performed (e.g., executed) at the management module 130 via the user interface 160 and/or receive an output signal from the onboard engine 130 at, for example, a display (not shown) of the user interface 160. For example, in some embodiments, a user can manage at least a portion of the database 124 via the user interface 160. In some embodiments, the user interface 160 can be a graphical user interface (GUI).

As shown in FIG. 1, an integer number of data center units 180 (which can each have hardware resources managed based on the same set of predefined hardware resource limit values) are assigned to (e.g., reserved for use by) the user 50. A request for a specified number or a change in a number of the data center units, such as the data center units 180 shown in FIG. 1, can be received at the management module 130. In some embodiments, the request can be defined in response to an input from the user 50. In other words, the user can make a request for a specified number of data center units via the user interface 160.

A value representing the number of data center units can be stored in a database 124 within a memory 120 of the management module 130. Each number can represent the hardware resources collectively managed as a data center unit. In some embodiments, the value can be associated with an identifier representing the user 50. An example of a database storing information related to data center units assigned to a user is shown in FIG. 2.

FIG. 2 is a schematic diagram that illustrates a database 200 that can be stored in a memory of a management module, according to an embodiment. The database 200 can be stored in a memory such as the memory 120 of the management module 130 shown in FIG. 1. As shown in FIG. 2, data center units DC₁ through DC_(N) (shown in the column labeled data center units 230) are assigned to a user represented by the user identifier “A” (shown in the column labeled user identifier 210), and data center units DC_(R) through DC_(R+M) (shown in the column labeled data center units 230) are assigned to a user represented by user identifier “B” (shown in the column labeled user identifier 210). The number of data center units (column 220) assigned to user A is represented by the value N, and the number of data center units (column 220) assigned to user B is represented by the value M. In some embodiments, the values “N” and “M” can be integer numbers.

As shown in FIG. 2, virtual resources AVR₁ through AVR_(Q) (shown in the column labeled virtual resources 240) are associated with user A, and virtual resources BVR₁ through BVR_(S) (shown in the column labeled virtual resources 240) are associated with user B. Although not shown in FIG. 2, the database 200 can also be defined to represent which of the data center resources of the data center units are operating each of the virtual resources. For example, although not shown, the database 200 can be configured to store information representing that data center resources defining data center unit DC₂ are operating virtual resources AVR₄ through AVR_(Q). In some embodiments, the virtual resources 240 can be configured to emulate one or more functions of, for example, a legacy source device being migrated to the virtual resources 240. More details related to migration of a source to a data center to be emulated as one or more virtual resource are described in connection with co-pending patent application bearing attorney docket no. VITU-002/00US 311331-2002, filed on same date, entitled, “Methods and Apparatus Related to Migration of Customer Resources to Virtual Resources within a Data Center Environment,” and co-pending patent application bearing attorney docket no. VITU-001/00US 311331-2001, filed on same date, entitled, “Methods and Apparatus for Movement of Virtual Resources within a Data Center Environment,” which are both incorporated herein by reference in their entireties.

In some embodiments, the database 200 can be dynamically updated to represent changes in resources (e.g., software resources, hardware resources) such as a decrease or increase in a number of data center resources assigned to the one or more of the users. Specifically, values representing the number of data center units 220 and assigned to a user represented by the user identifiers 210 can be dynamically modified.

Referring back to FIG. 1, in some embodiments, the user 50 can request, via the user interface 160, an increase in a number of data center units (such as data center units 180) assigned to the user 50. Accordingly, a request to change a value representing the number of data center units assigned to the user 50 can be received at the management module 130. The value can be stored at the memory 120 of the management module 130. A request to increase a number of data center units can be referred to as an increase request. The request can be received at the management module 130 from the user interface 160.

In response to an increase request, the management module 130 can be configured to determine whether or not resources of the data center 100 are available to be assigned to the user 50 as resources of a data center unit. In some embodiments, the management module 130 can be configured to store inventory information representing resources available at the data center 100 in the memory 120, for example, in database 124. In such embodiments, the management module 130 can be configured to access the inventory information and determine, based on the inventory information, whether one or more data center units, or hardware resources of one or more data center units, (not shown) are available to be assigned to a user such as user 50. In some embodiments, inventory information representing an unassigned pool of resources and/or data center units (or hardware of data center units) can be stored in the memory 120. An example of inventory information that can be stored in the database 124 of the memory 120 is shown in FIG. 3.

FIG. 3 is a schematic diagram that illustrates a database 300 that includes information about the availability of data center resources, according to an embodiment. As shown in FIG. 3, the data center units (or hardware resources of data center units) represented by identifiers U1 and U3 (shown in column 320) are not available for assignment to a user because, as indicated in column 310, these data center units are already assigned to a user. The data center units represented by identifiers U2, U4, and U5 (shown in column 320) are available for assignment to a user because, as indicated in column 310, these data center units not assigned to a user. In some embodiments, the data center units represented by identifiers U2, U4, and U5, because they are not assigned, can be referred to as a pool of unassigned data center resources, or as a pool of unassigned data center units.

Although not shown, in some embodiments, a database can be configured to store inventory information related to individual hardware resources (e.g., processor, network interface cards, storage devices) that can be managed as a data center unit. Specifically, the availability or unavailability of the individual hardware resources (or portions thereof) can be stored in the database. Based on this inventory information about the hardware resources (or portions of the hardware resources), a management module (such as management module 130 shown in FIG. 1) can determine whether or not hardware resources may be available to define a data center unit that can be assigned to a user.

Referring back to FIG. 1, if a data center unit (not shown) is available for assignment to user 50 (or if hardware resources of the data center 100 are available to be managed as a data center unit that can be assigned to user 50), the management module 130 can be configured to assign the available data center unit to user 50 so that the hardware resources of the data center unit can be used by, for example, a virtual resource associated with the user 50. In other words, if a sufficient number of data center units are available to satisfy the increase request, the management module 130 can grant the request and assign the data center unit(s) to the user 50. The data center units that are assigned to the user 50 can be removed from, for example, a pool of unassigned resources (or data center units). In some embodiments, one or more data center units that are assigned to a user in response to an increase request can have a status associated with the data center unit(s) changed from an available status to an unavailable status. In some embodiments, the availability or unavailability of a data center unit (or hardware resources that can be used to define a data center unit) can be determined based on inventory information stored in the memory 120.

In some embodiments, the user 50 can request, via the user interface 160, a decrease in a number of data center units (such as data center units 180) assigned to the user 50. Accordingly, a request to change a value representing the number of data center units (which can represented hardware resources collectively managed as a data center unit) assigned to the user 50 can be received at the management module 130. A request to decrease a number of data center units can be referred to as an decrease request. The request can be received at the management module 130 from the user interface 160.

In some embodiments, hardware resources of a data center unit removed from a set of data center units previously assigned to a user can be reassigned to another user. For example, if hardware resources managed as a data center unit DU2 are removed from the set of data center units 180 in response to a decrease request from the user 50, the hardware resources managed as data center unit DU2 can be assigned to another user (not shown). The reassignment can be represented in a database 124 stored in the memory 120. In some embodiments, the data center unit DU2 (e.g., the hardware resources of the data center unit DU2) can be returned to a pool of unassigned data center units.

In some embodiments, the memory 120 can be, for example, a random-access memory (RAM) (e.g., a dynamic RAM, a static RAM), a flash memory, a removable memory, and/or so forth. In some embodiments, the database 124 can be implemented as, for example, a relational database, an indexed database, a table, and/or so forth. Although the memory 120 and the database 124 are shown as being local to the management module 130, in some embodiments, one or more portions of the database 124 can be stored in a remote memory that can be accessed by the management module 130. For example, the portions of the database 124 can be stored in a separate (e.g., a remote) storage device (e.g., storage facility) that can be accessed by the management module 130 via a network (e.g., a local area network (LAN), a wide area network (WAN)) (not shown).

As shown in FIG. 1, the management module 130 can include a monitoring module 134. The monitoring module 134 can be configured to trigger a change in a number of data center units (such as data center units 180) assigned to a user (such as user 50) based on one or more values representing performance associated with the hardware resources of data center units. The values representing performance can be referred to as performance metric values. In some embodiments, the monitoring module 134 can be configured to trigger an increase or a decrease in a number of data center units assigned to user 50 in response to a threshold condition being satisfied based on one or more performance metric values.

For example, the monitoring module 134 can be configured to remove data center unit DU2 from the set of data center units 180 assigned to user 50 in response to a performance metric value indicating that the data center units 180 collectively are being under-utilized. In some embodiments, the monitoring module 134 can be configured to add an additional data center unit (not shown) (or hardware resources of the additional data center unit) to the set of data center units 180 assigned to user 50 in response to a performance metric value indicating that the hardware resources of data center units 180 collectively are being over-utilized. The over-utilization can be manifested in, for example, failure data. In some embodiments, the monitoring module 134 can be configured to replace one or more data center units (such as data center units 180) assigned to a user (such as user 50) based on a threshold condition being satisfied based on a performance metric value. In some embodiments, the monitoring module 134 can be configured to modify a number of data center assigned to a user by modifying a value stored in a database (such as database 124) that represents a number of data center units.

FIG. 4 is a graph that illustrates values of a performance metric, according to an embodiment. As shown in FIG. 4, the values of the performance metric (shown on the y-axis) are plotted versus time (shown on the x-axis). The values of the performance metric are above a lower limit value (shown as “LL”) before time T1, and the values of the performance metric are below the lower limit value after time T1. A monitoring module, such as monitoring module 134 shown in FIG. 1, can be configured to modify a number of data center units assigned to a user in response to the values of the performance metric falling below the lower limit value at time T1. In other words, the monitoring module can modify the number of data center units assigned to the user in response to the values of the performance metric satisfying a threshold condition associated with the lower limit value at time T1.

Referring back to FIG. 1, the monitoring module 134 can be configured to modify a number of data center units assigned to a user (such as user 50) based on various performance metric values, such as, for example, a capacity value, a value representing a failure rate, a utilization value, and/or so forth. In some embodiments, the performance metric values can be associated with a specified period of time.

In some embodiments, the monitoring module 134 can be configured to receive the values (e.g., pushed values, pulled values) representing the performance metric from the data center 100 (or a portion thereof). For example, in some embodiments, the monitoring module 134 can be configured to receive one or more performance metric values produced by virtual resources operating within the hardware resources of data center units of the data center 100. In some embodiments, the performance metric values can be received periodically, randomly, in a preselected manner, and/or in response to a request from the monitoring module 134. In some embodiments, the monitoring module 134 can be configured to request and receive data from one or more resources (e.g., hardware resources, software resources, virtual resources) of the data center 100 that can be used to calculate a performance metric value.

In some embodiments, the monitoring module 134 can be configured to send a notification to, for example, the user 50 via user interface 160, indicating that a number of data center units assigned to the user 50 should be modified. In some embodiments, the monitoring module 134 can be configured to modify a number of data center units (by modifying a value representing the number of data center units) assigned to the user 50 only when authorized to do so by the user. In some embodiments, the monitoring module 134 can be configured to solicit authorization from the user 50 via the user interface 160 for modification of the number of the data center units 180. When authorization is received from the user 50 via the user interface 160 the monitoring module 134 can be configured to modify the number of data center units 180 assigned to the user 50.

In some embodiments, the management module 130 can be configured to identify a minimum number of data center units (such as data center units 180) to operate a virtual resource. For example, the management module 130 can be configured to identify (or calculate) a minimum number of data center units (based on one or more assessment parameter values) to operate a virtual resource within a data center environment. In some embodiments, the management module 130 can be configured to determine that a particular minimum number of data center units are used to operate a virtual resource emulating, for example, at least a portion of a particular physical device. In some embodiments, the number of discrete data center units selected to operate a virtual resource (or set of virtual resources) can be determined by the management module 130 based on, for example, an ability of the data center units to handle burst processing levels of the virtual resource(s) and/or an average processing level of the virtual resource(s). In some embodiments, the calculations related to numbers of data center units to operate a virtual resource can be performed by an assessment module portion (not shown) of the management module 130. More details related to an assessment module are described in connection with co-pending patent application bearing attorney docket no. VITU-002/00US 311331-2002, filed on same date, entitled, “Methods and Apparatus Related to Migration of Customer Resources to Virtual Resources within a Data Center Environment,” which has been incorporated herein by reference in its entirety.

In some embodiments, the monitoring module 134 can be configured to modify a number of data center units assigned to the user 50 based on a user preference of the user 50. In some embodiments, the user preference can identify the performance metric values to be used by the monitoring module 134 to modify a number of data center units (such data center units 180 shown in FIG. 1) assigned to a user. In some embodiments, the user preference can identify one or more threshold conditions to be used the monitoring module 134 to modify a number of data center units assigned to the user 50. In some embodiments, one or more user preferences can be stored in memory 120.

As shown in FIG. 2, a user preference UA (shown in column 250) is associated with the user represented by user identifier A (shown in column 210), and a user preference UB (shown in column 250) is associated with the user represented by user identifier B (shown in column 210). The user preference UA and UB can represent user preferences related to monitoring of data center units (which are shown in column 230). In some embodiments, the monitoring module 134 can be configured to access the user preferences 250 and can be configured modify the number of data center units (shown in column 220) based on the user preferences 250.

In some embodiments, one or more portions of the management module 130 can be (or can include) a hardware-based module (e.g., an application-specific integrated circuit (ASIC), a digital signal processor (DSP), a field programmable gate array (FPGA)) and/or a software-based module (e.g., a module of computer code, a set of processor-readable instructions that can be executed at a processor). Although not shown, in some embodiments, the management module 130 can include one or more memory portions (e.g., a random access memory (RAM) portion, a shift register, a cache) that can be used during operation of one or more functions of the management module 130. In some embodiments, one or more of the functions associated with the management module 130 can be included in different modules and/or combined into one or more modules.

Although not shown, in some embodiments, the hardware resources and/or software resources of the data center 100 can include one or more levels of infrastructure. For example, in some embodiments, the hardware resources of the data center 100 can include, host devices (e.g., server devices), storage devices, access switches, aggregation devices, routers, interface components, cables, and/or so forth. For example, the data center 100 can be configured so that host devices (which can be configured to host virtual resources) and/or storage devices can be in communication with (e.g., coupled to) a layer of access switches that are in communication with (e.g., coupled to) a layer of aggregation devices. The aggregation devices can function as gateway devices into a set of routers/switches that function as core switching elements of the data center 100.

In some embodiments, the software resources of the data center 100 can include, for example, management modules, operating systems, hypervisors (e.g., VMware hypervisor, Xen hypervisor, Hyper-V hypervisor), and/or so forth. In some embodiments, the data center 100 can be a cloud computing environment where hardware resources and/or software resources are shared by multiple virtual resources associated with one or more users (e.g., clients, customers). In some embodiments, the virtualized environment defined by the data center 100 can be referred to as a data center virtualized environment. In some embodiments, the software resources of the data center 100 can include, for example, management modules, operating systems, hypervisors, and/or so forth. The hypervisors can be configured to facilitate virtualization of hardware resources of host devices. The operating systems can be installed at routers, aggregation devices, routers, core switching elements, and/or forth.

In some embodiments, the management module 130 can be a centralized management module configured to handle data center management for the entire data center 100, or can be a de-centralized management module configured to handle management of only a portion of the data center 100. In some embodiments, the management module 130 can be configured to perform various functions in addition to management of data center units such as data center units 180. For example, the management module 130 can be configured to handle disaster recovery, migration of virtual resources to a data center, and/or so forth. More details related to a management module configured to perform various operations related to a data center environment are set forth in co-pending patent application bearing attorney docket no. VITU-004/00US 311331-2004, filed on same date, entitled, “Methods and Apparatus for Data Center Management Independent of Hypervisor Platform,” which is incorporated herein by reference in its entirety.

In some embodiments, the data center 100 can be managed locally or can have consolidated management. For example, the entire data center 100, or a portion thereof, can be managed via a single management module (not shown). In some embodiments, the entire data center 120, or a portion thereof, can be managed via multiple management modules (not shown) that can be distributed through the data center 100 infrastructure. In some embodiments, some functionality of the data center 100 can be managed based on a consolidated management scheme, while other functionality of the data center 100 can be managed based on a distributed management scheme.

FIG. 5 is a schematic diagram that illustrates resources controllers 570 in communication with a data center 500, according to embodiment. As shown in FIG. 5, the resource controllers 570 include a processor (e.g., a central processing unit (CPU)) controller 540, a memory controller 542, a network controller 544, a storage input/output operations per second (IOPS) controller 546, a storage controller 548, and a storage bandwidth controller 550. In some embodiments, the resources controllers 570 can include, for example, a VMware capacity planning tool, a VMware vSphere controller, a Converged Network Adapter controller, a Compellent SAN controller, and/or so forth.

Each of the resource controllers 570 shown in FIG. 5 are configured to manage resources associated with a particular type of hardware of a data center 500. As represented in FIG. 5, the resource controllers 570 can be configured to manage a portion of the data center unit 580. Accordingly, the resources controllers 570 collectively manage the hardware resources of data center unit 580. One or more of the resources controller 570 shown in FIG. 5 can be included in the resource controller 170 shown in FIG. 1.

In some embodiments, the processor controller 540 can be configured to manage the resources of one or more processors (not shown) of the data center 500 so that a certain portion of the computing cycles of the processor(s) are reserved for the data center unit 580. In other words, the computing cycles can be reserved so that if the computing cycles are needed by a virtual resource of a user to whom the data center unit 580 is assigned, the computing cycles will be available for use by the virtual resource of the user. For example, in some embodiments, computing cycles substantially equivalent to, for example, a 100 MHz processor, a 1.5 GHz processor, or so forth, can be reserved for the data center unit 580. In some embodiments, a hardware resource limit value specific to the processor controller 540 can be referred to as a processor limit value.

In some embodiments, the memory controller 542 can be configured to manage the resources of one or more memory components (not shown) of the data center 500 so that a certain portion of the memory component(s) can be reserved for the data center unit 580. For example, in some embodiments, a memory storage capacity of 1 MB, 10 MB, or so forth, of a memory component can be reserved for the data center unit 580. In some embodiments, a hardware resource limit value specific to the memory controller 542 can be referred to as a memory limit value.

In some embodiments, the network controller 544 can be configured to manage the resources of one or more network components (e.g., network interface cards) (not shown) of the data center 500 so that a certain portion of processing power of the network component(s) can be managed (e.g., reserved) as part of the data center unit 580. For example, in some embodiments, a data transfer capacity of a network component can be time-division multiplexed so that a specified level of network bandwidth substantially equal to, for example, 5 Mb/s, 100 Mb/s, 1 Gb/s, or so forth, can be managed for the data center unit 580. In some embodiments, a hardware resource limit value specific to the network controller 544 can be referred to as a network limit value.

In some embodiments, a storage IOPS controller 546 can be configured to manage the resources of one or more storage components (e.g., hard disk drive, server storage) (not shown) of the data center 500 so that a certain IO capacity of the storage component (e.g., more than 1 IOPS, 50 IOPS) can be managed for (e.g., reserved for) the data center unit 580. In some embodiments, a hardware resource limit value specific to the storage IOPS controller 546 can be referred to as an IOPS limit value.

In some embodiments, a storage controller 548 can be configured to manage the resources of one or more storage components so that a certain portion of storage capacity of the storage component(s) (e.g., 50 GB, 100 GB, 10 Terabytes (TB)) can be reserved for the data center unit 580. In some embodiments, a hardware resource limit value specific to the storage controller 548 can be referred to as a storage limit value.

In some embodiments, a storage bandwidth controller 550 can be configured to manage the bandwidth of one or more storage components so that a certain portion of the bandwidth (e.g., 10 Mb/s, 1 Gb/s) can be managed (e.g., reserved) for the data center unit 580. In some embodiments, a hardware resource limit value specific to the storage bandwidth controller 542 can be referred to as a storage bandwidth limit value.

The resource controllers 570 can be triggered to reserve a specified portion of hardware resources of the data center 500 for the data center unit 580 based on one or more hardware resource limit values. The hardware resource limit values can be communicated to the resource controllers 570 in an instruction 60. In some embodiments, the instruction 60 can be defined in response to a request (e.g., an increase request, a decrease request) received at the management module 530 from the user interface (UI) 560. As shown in FIG. 5, the management module 530 can be executed within a processor 594 of a processing device 590. The processing device 590 can also include a memory 592 (e.g., a storage device, a buffer, a RAM) configured to facilitate the functions of, for example, the management module 530. For example, the memory 592 can be used by the management module 530 during communication with the resource controllers 570.

As shown in FIG. 5, the instruction 60 can be sent to each of the resource controllers. The instruction 60 can include hardware resource limit values for each of the resource controllers within the resource controller 570. For example, with respect to the memory controller 542, the instruction 60, which can include hardware resource limit values specific to each of the resource controllers within the resource controller 570, can be defined at the management module 530 and sent to the memory controller 542. The memory controller 542 can be configured to parse a hardware resource limit value specific to the memory controller 542 from the instruction 60. The memory controller 542 can be configured to manage hardware resources of the data center 500 for use as the data center unit 580 based on the hardware resource limit value.

Although not shown, in some embodiments, the management module 530 can be configured to define and send two or more different instructions to each of the resource controllers within the resource controllers 570. The different instructions can be sent to the resource controllers 570 because some of the resource controllers can be configured to operate based on different platforms (e.g., hardware and/or software platforms, protocols) than other resource controllers from the resource controller 570. For example, the management module 530 can be configured to send a first instruction (which includes a network limit value) based on a first application programming interface (API) to the network controller 544, and send a second instruction (which includes a storage limit value) based on a second API to the storage controller 548.

Although six different types of resource controllers are shown in the resource controllers 570, in some embodiments, a different combination of resource controllers can be used to manage the hardware resources of data center unit 580. For example, less than all of the resource controllers 570 shown in FIG. 5 can be used to manage the hardware resources of data center unit 580. In some embodiments, a different resource controller such as a bus speed resource controller can be used to manage a bus portion of the data center unit 580. In some embodiments, the instruction 60 (or set of instructions) can be configured to trigger all or a portion of the resource controllers 570 to manage the hardware resources of the data center unit 580 in a customized fashion.

Although shown as being separate from the management module 530 in FIG. 5, in some embodiments, one or more of the resource controllers 570 can be integrated into the management module 530. In some embodiments, one or more functions of the resources controller 570 can be included as a function of the management module 530. Although not shown, in some embodiments, the resource controllers 570 can include a software resource controller.

FIG. 6 is a flowchart that illustrates a method for modifying a set of data center units based on a performance metric, according to an embodiment. As shown in FIG. 6, a value of a performance metric representing performance of a set of virtual resources associated with a user identifier is received, at 600. The set of virtual resources can be associated with a user (based on a user identifier representing the user). In some embodiments, the performance metric can be, for example, related to a failure rate of the virtual resources. In some embodiments, the performance metric can be optionally specified in a user preference 630 associated with the user, or can be based on a default value.

A set of data center units assigned to operate the set of virtual resources is modified in response to the performance metric satisfying a threshold condition, at 610. In some embodiments, a number of data center units mapped to the set of virtual resources can be increased or decreased. In some embodiments, the threshold condition can be optionally defined within the user preference 630 associated with a user, or can be based on a default value.

FIG. 7 is a flowchart that illustrates a method for modifying a number of data center units in response to a request, according to an embodiment. Each number can represent hardware resources collectively managed as a data center unit. As shown in FIG. 7, a request for a change in a value representing a number of data center units included in a set of data center units assigned to a user is received, at 700. The request can be triggered by the user and can be received at a management module from a user interface. In some embodiments, the number of data center units assigned to the user can be represented by a value in a database stored in a memory.

If the request is an increase request, at 710, the availability of an additional data center unit is determined, at 720. The availability can be determined based on information about a pool of unassigned data center units stored in a database. As shown in FIG. 7, the additional data center unit is assigned to the user, at 740, when the data center unit is available, at 730.

When the additional data center units are not available, at 730, the request is denied, at 750. In some embodiments, the additional data center units may not be available because they are assigned to another user, or because resources (e.g., hardware resources, software resources) managed as a data center unit are not available. In some embodiments, the request may not be denied, but can instead be assigned a pending state (e.g., a held state) until resources (e.g., hardware resources, software resources) that can be assigned to the user become available. In other words, the request can be pending until resources that can be managed as a data center unit (and can be assigned to the user) become available. In some embodiments, the request can be queued with other requests in a request queue. In some embodiments, a queue of requests can be handled in a first-in-first-out (FIFO) fashion, or in some other order.

If the request is an decrease request, at 710, at least one data center unit is included in a pool of unassigned data center units, at 750. An assignment of the data center unit(s) can be modified so that they are no longer assigned to the user and instead included in a pool of unassigned data center units. In other words, a representation of the data center unit(s) are included in a pool of unassigned data center units so that, for example, a management module can identify these data center unit(s) as not being assigned to a user. Although not shown, in some embodiments, a management module, for example, can be configured to reassign one or more of the data center units to another user rather than include the data center unit(s) in the pool of unassigned data center units.

Some embodiments described herein relate to a computer storage product with a computer-readable medium (also can be referred to as a processor-readable medium) having instructions or computer code thereon for performing various computer-implemented operations. The media and computer code (also can be referred to as code) may be those designed and constructed for the specific purpose or purposes. Examples of computer-readable media include, but are not limited to: magnetic storage media such as hard disks, floppy disks, and magnetic tape; optical storage media such as Compact Disc/Digital Video Discs (CD/DVDs), Compact Disc-Read Only Memories (CD-ROMs), and holographic devices; magneto-optical storage media such as optical disks; carrier wave signal processing modules; and hardware devices that are specially configured to store and execute program code, such as Application-Specific Integrated Circuits (ASICs), Programmable Logic Devices (PLDs), and Read-Only Memory (ROM) and Random-Access Memory (RAM) devices.

Examples of computer code include, but are not limited to, micro-code or micro-instructions, machine instructions, such as produced by a compiler, code used to produce a web service, and files containing higher-level instructions that are executed by a computer using an interpreter. For example, embodiments may be implemented using, for example, a run-time environment and/or an application framework such as a Microsoft .NET framework and/or Java, C++, or other programming languages (e.g., object-oriented programming languages) and/or development tools. Additional examples of computer code include, but are not limited to, control signals, encrypted code, and compressed code.

While various embodiments have been described above, it should be understood that they have been presented by way of example only, not limitation, and various changes in form and details may be made. Any portion of the apparatus and/or methods described herein may be combined in any combination, except mutually exclusive combinations. The embodiments described herein can include various combinations and/or sub-combinations of the functions, components and/or features of the different embodiments described. For example, multiple management modules can be configured to cooperatively handle assignment of data center units to one or more users. 

What is claimed is:
 1. A method for managing virtual resources, the method comprising: managing virtual resources within a data center environment, the data center environment including a plurality of data center units, each data center unit including a grouping of different types of hardware resources which collectively meet predefined hardware resource limit values common to all data center units, the managing using a database configured to keep track of and manage resources by processing the virtual resources as a function of the data center units, the database configured with fields for user identifier information, quantity of data center units assigned to each user, unit-based listings of data center units assigned to each user, virtual resource information regarding virtual resources associated with each user, and user preference information; processing a request to change a value representing a number of data center units included in a set of data center units assigned to a user, and determining, in response to the request, whether hardware resources of a data center unit mutually exclusive from hardware resources of the set of data center units and managed based on the set of predefined resource limit values are available for assignment to the user when the request to change is an increase request.
 2. The method of claim 1, wherein at least a portion of the data center units from the set of data centers units are configured to operate a set of virtual resources at a guaranteed service level.
 3. The method of claim 1, further comprising: removing a data center unit from the set of data center units when the request to change is a decrease request.
 4. The method of claim 1, further comprising: modifying a distribution of a set of virtual resources operating within the set of data center units when the request to change is a decrease request such that the set of virtual resources operate within a first subset of the set of data center units before the code to modify is executed and operate within a second subset of the set of data center units different from the first subset of the set of data center units after the code to modify is executed.
 5. The method of claim 1, further comprising: identifying a data center unit for removal from the set of data center units when the request to change is a decrease request; and associating the data center unit with a pool of unassigned data center units.
 6. The method of claim 1, wherein the user is a first user, the method further comprising: reassigning a data center unit from the set of data center units associated with the first user to a set of data center units associated with a second user when the request to change is a decrease request.
 7. The method of claim 1, further comprising: sending a notification that the request to change has been denied when the hardware resources are unavailable for assignment to the user.
 8. The method of claim 1, wherein the set of predefined hardware resource limit values includes: at least one of a processor speed limit value, a memory space limit value, or a network bandwidth limit value; and at least one of a disk space limit value, a disk bandwidth limit value, or a disk input/output limit value.
 9. An apparatus, comprising: a memory configured to store information representing assignment of a set of data center units to a user identifier, and a management module configured to: manage virtual resources within a data center environment, the data center environment including a plurality of data center units, each data center unit including a grouping of different types of hardware resources which collectively meet predefined hardware resource limit values common to all data center units, the managing using a database configured to keep track of and manage resources by processing the virtual resources as a function of the data center units, the database configured with fields for user identifier information, quantity of data center units assigned to each user, unit-based listings of data center units assigned to each user, virtual resource information regarding virtual resources associated with each user, and user preference information; and modify a value representing a number of data center units included in the set of data center units in response to at least one of (1) a request associated with the user identifier, or (2) a threshold condition being satisfied based on a change in performance of a set of virtual resources operating within the set of data center units.
 10. The apparatus of claim 9, wherein the management module is configured to send a plurality of instructions related to modification of the value representing the number of data center units to a plurality of resource controllers, each resource controller from the plurality of resource controllers is configured to implement the predefined resource limit values.
 11. The apparatus of claim 9, wherein at least a portion of the data center units from the set of data centers units are configured to operate the set of virtual resources associated with user identifier at a guaranteed service level.
 12. The apparatus of claim 9, wherein the memory is further configured to store a user preference, the management module is configured to modify the value representing the number of data center units based on the user preference.
 13. The apparatus of claim 9, wherein the memory is further configured to store a user preference, the threshold condition being defined within the user preference.
 14. The apparatus of claim 9, wherein the management module is configured to operate for a plurality of hypervisor platforms, the set of virtual resources being associated with one of the plurality of hypervisor platforms.
 15. A method of managing virtual resources, the method comprising: managing virtual resources within a data center environment, the data center environment including a plurality of data center units, each data center unit including a grouping of different types of hardware resources which collectively meet predefined hardware resource limit values common to all data center units the managing, using a database configured to keep track of and manage resources by processing the virtual resources as a function of the data center units, the database configured with fields for user identifier information, quantity of data center units assigned to each user, unit-based listings of data center units assigned to each user, virtual resource information regarding virtual resources associated with each user, and user preference information; processing information representing that a set of data center units is assigned to operate a set of virtual resources, processing an indicator representing that a utilization value of at least a portion of the set of virtual resources, when operating within the set of data center units, has satisfied a threshold condition; and modifying a value representing a number of data center units included in the set of data center units in response to the indicator.
 16. The method of claim 15, wherein the threshold condition is satisfied when the utilization value is below a specified value for a specified period of time, the threshold condition is based on a user preference.
 17. The method of claim 15, wherein a magnitude of the modification of the value representing the number of data center units is based on a magnitude of the utilization value relative to the threshold condition.
 18. The method of claim 15, wherein the value representing the number of data center units represents a minimum number of data center units to operate the set of virtual resources at a guaranteed service level.
 19. The method of claim 15, wherein the threshold condition is satisfied when a guaranteed service level is maintained.
 20. The method of claim 15, further comprising: receiving authorization from a user to modify the value representing the number of data center units before modifying the value representing the number of data center units. 